Comments
-
Use the CLI for this and the command for 6.5 is: config access-rule ipv4 uuid "rule uuid" no packet-monitoring exit To do this for all rules you will need to get the UUID for each one. It's easier to run this on all rules than to find out which ones have the feature enabled. To get the UUIDs, run the following command in…
-
Hello, it will use the WAN IP entered in the IPsec Primary Gateway Name or Address field.
-
Disable Keep Alive for now and on the General tab, remove the values for Local IKE ID and Peer IKE ID from both Sonicwalls.
-
@preston Thank you for the input. The unsupported firewall predates 5.9. I understand the overall concept and yes the devices at Site A and C use the same Gateway IP. I will hash it out though. @BWC Agreed, it is a lot of overhead which was expected given the setup but a Mikrotik might just be the solution. We already have…
-
@preston Yes, some devices are still at A and others at C. I am working with 3 different and distant generations of SonicWalls and Site B does not support route-based tunnel interfaces. However, I could do a tunnel interface between A and C. Would I then be able to route traffic from B to A to C?